Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 510c3d09bfc04d74eb836e50a42d354ea0274521570f484f1afc910b1c915dca

Tx prefix hash: 542bd50bf5c23c7ccd954fc8dfc2120bcdd1f1e465e38cb022fbceb5ed57114a
Tx public key: c5429b581e1de827e620774cc86801e6455898e26c15b0ae6dae960203340fbc
Timestamp: 1703250911 Timestamp [UCT]: 2023-12-22 13:15:11 Age [y:d:h:m:s]: 01:341:16:42:02
Block: 918698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503077 RingCT/type: yes/0
Extra: 01c5429b581e1de827e620774cc86801e6455898e26c15b0ae6dae960203340fbc021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2efb10ba98c1e0dcbae0c60d81dc2fbddc977db3a74ab2e26f17ce7b724fd8eb 0.600000000000 1376356 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": 918708, "vin": [ { "gen": { "height": 918698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2efb10ba98c1e0dcbae0c60d81dc2fbddc977db3a74ab2e26f17ce7b724fd8eb" } } ], "extra": [ 1, 197, 66, 155, 88, 30, 29, 232, 39, 230, 32, 119, 76, 200, 104, 1, 230, 69, 88, 152, 226, 108, 21, 176, 174, 109, 174, 150, 2, 3, 52, 15, 188, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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