Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e314eae6e2b5febd4f0ebb264e074d34b04ff49180952d73660b63ac1d572af9

Tx prefix hash: 3f94904b648d1e88b4a2f46e0c9acaf4036d54f6622d629738ecaef73254aa4e
Tx public key: 204a54b01c8faacadc0a12605cbfbf53ba0cc60d5a90c759035d27b243457735
Timestamp: 1714238647 Timestamp [UCT]: 2024-04-27 17:24:07 Age [y:d:h:m:s]: 01:028:01:51:19
Block: 1009787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281030 RingCT/type: yes/0
Extra: 01204a54b01c8faacadc0a12605cbfbf53ba0cc60d5a90c759035d27b2434577350211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9f405c83d91d57aa34a28f94e8659aa7a6f9def27575a4c571c1d6eb8361b2 0.600000000000 1471559 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": 1009797, "vin": [ { "gen": { "height": 1009787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9f405c83d91d57aa34a28f94e8659aa7a6f9def27575a4c571c1d6eb8361b2" } } ], "extra": [ 1, 32, 74, 84, 176, 28, 143, 170, 202, 220, 10, 18, 96, 92, 191, 191, 83, 186, 12, 198, 13, 90, 144, 199, 89, 3, 93, 39, 178, 67, 69, 119, 53, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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