Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 700f4cf3cf717bb6e93229c6e33db1cda201c82311bfd296450234f1f3ba6d05

Tx prefix hash: b57832dd07b20d3ec95e2e4341446e1750fca834fca51031b30bb9c70f8bf939
Tx public key: 1ce47bd36d592c96762da079c24b2d162266e60769ab596d4406ff884bc4aa2f
Timestamp: 1655847960 Timestamp [UCT]: 2022-06-21 21:46:00 Age [y:d:h:m:s]: 02:215:18:15:39
Block: 527479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 675472 RingCT/type: yes/0
Extra: 011ce47bd36d592c96762da079c24b2d162266e60769ab596d4406ff884bc4aa2f02110000000475e3f0e9000000000000000000

1 output(s) for total of 10.970925637000 dcy

stealth address amount amount idx
00: c276ae4ca8b1ad60e6a74675a9bffe3a06ffe2a0e36a407aeb95e57052ca7fde 10.970925637000 956158 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": 527489, "vin": [ { "gen": { "height": 527479 } } ], "vout": [ { "amount": 10970925637, "target": { "key": "c276ae4ca8b1ad60e6a74675a9bffe3a06ffe2a0e36a407aeb95e57052ca7fde" } } ], "extra": [ 1, 28, 228, 123, 211, 109, 89, 44, 150, 118, 45, 160, 121, 194, 75, 45, 22, 34, 102, 230, 7, 105, 171, 89, 109, 68, 6, 255, 136, 75, 196, 170, 47, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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