Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469137f32b581a2c2db4dcbf870a97e4b221b8350a8d6c13ebbd67dc91def1ba

Tx prefix hash: c4627fe56d5442bc5984771c8d7b9f45b71392aef5c583bedf56dff9780ffa6a
Tx public key: b0a87d2424d24e6801599cee9fa9aa799aefb6421f3f9ee0a6f5188ffdf73177
Timestamp: 1745692452 Timestamp [UCT]: 2025-04-26 18:34:12 Age [y:d:h:m:s]: 00:011:23:46:24
Block: 1270052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8558 RingCT/type: yes/0
Extra: 01b0a87d2424d24e6801599cee9fa9aa799aefb6421f3f9ee0a6f5188ffdf731770211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9557592eda5df6e2ebba86bb3806ee021683d3569cf2b9e69a465b19c03b1fa7 0.600000000000 1757293 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": 1270062, "vin": [ { "gen": { "height": 1270052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9557592eda5df6e2ebba86bb3806ee021683d3569cf2b9e69a465b19c03b1fa7" } } ], "extra": [ 1, 176, 168, 125, 36, 36, 210, 78, 104, 1, 89, 156, 238, 159, 169, 170, 121, 154, 239, 182, 66, 31, 63, 158, 224, 166, 245, 24, 143, 253, 247, 49, 119, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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