Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3bf1000ff554cc90a4b3d6bd0cba4dfb745c4cca2faff170b88016f50c5da5b5

Tx prefix hash: 098cd75e4e9a5e61faba6f973443bc98a3e0c11f9ed06416607be7faaac5126f
Tx public key: aecb4979e6f9fb47bd755abcf8e986a0e2620261c67cb258a634efd5f4bbe9a1
Timestamp: 1709163802 Timestamp [UCT]: 2024-02-28 23:43:22 Age [y:d:h:m:s]: 01:036:23:53:08
Block: 967726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287441 RingCT/type: yes/0
Extra: 01aecb4979e6f9fb47bd755abcf8e986a0e2620261c67cb258a634efd5f4bbe9a102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f74ab27011e0a9ad900cde30cf0e25b0d22ea9380ae22d98efa62d202859a8 0.600000000000 1427511 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 967736, "vin": [ { "gen": { "height": 967726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f74ab27011e0a9ad900cde30cf0e25b0d22ea9380ae22d98efa62d202859a8" } } ], "extra": [ 1, 174, 203, 73, 121, 230, 249, 251, 71, 189, 117, 90, 188, 248, 233, 134, 160, 226, 98, 2, 97, 198, 124, 178, 88, 166, 52, 239, 213, 244, 187, 233, 161, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8