Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1df2b55cf6611db548f24671b143b1d4034752d1f47f9a293035e0cd9dd77305

Tx prefix hash: cbb54c8c0b93e1d455f0850cc32b05fa02d65bc013a37be9dc52cc2bbb21d36d
Tx public key: 17694cf2ec57d9270e59d51efad233ec4ec8e102d326c602f6435f76b097d9a7
Timestamp: 1648640495 Timestamp [UCT]: 2022-03-30 11:41:35 Age [y:d:h:m:s]: 03:030:02:53:07
Block: 469546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 801818 RingCT/type: yes/0
Extra: 0117694cf2ec57d9270e59d51efad233ec4ec8e102d326c602f6435f76b097d9a7021100000007bf7ee4e7000000000000000000

1 output(s) for total of 17.068660267000 dcy

stealth address amount amount idx
00: 1fe3fc279b0621388f907b670ecbded747782ee62417242e5300b8417d43fd8c 17.068660267000 888508 of 0

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": 469556, "vin": [ { "gen": { "height": 469546 } } ], "vout": [ { "amount": 17068660267, "target": { "key": "1fe3fc279b0621388f907b670ecbded747782ee62417242e5300b8417d43fd8c" } } ], "extra": [ 1, 23, 105, 76, 242, 236, 87, 217, 39, 14, 89, 213, 30, 250, 210, 51, 236, 78, 200, 225, 2, 211, 38, 198, 2, 246, 67, 95, 118, 176, 151, 217, 167, 2, 17, 0, 0, 0, 7, 191, 126, 228, 231, 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