Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c91c507d9cb10c26e0301ec54d0b2b848f6c00a00c8dd40b88176fc3a258e547

Tx prefix hash: 382b7b544d772bff148df6f09fb44df4c3fb6b682327cdaf3838680e2162605d
Tx public key: 047535178b1d91801fe8ed1f4d44394c88f8d98ce0c15780884bea288d11c8bc
Timestamp: 1717235030 Timestamp [UCT]: 2024-06-01 09:43:50 Age [y:d:h:m:s]: 00:298:03:21:22
Block: 1034640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213055 RingCT/type: yes/0
Extra: 01047535178b1d91801fe8ed1f4d44394c88f8d98ce0c15780884bea288d11c8bc0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6b412b04daf9bdd9375fa112e3c452d09fc6bd98f77fc3b3d5c4821d6661d1c 0.600000000000 1503155 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": 1034650, "vin": [ { "gen": { "height": 1034640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6b412b04daf9bdd9375fa112e3c452d09fc6bd98f77fc3b3d5c4821d6661d1c" } } ], "extra": [ 1, 4, 117, 53, 23, 139, 29, 145, 128, 31, 232, 237, 31, 77, 68, 57, 76, 136, 248, 217, 140, 224, 193, 87, 128, 136, 75, 234, 40, 141, 17, 200, 188, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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