Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb95e3fd5f3335a0f86883ccb1aeaa471a26641c9e581eac2d0bf32a326de977

Tx prefix hash: 731bf4686f662a837f8395a9df27a0fb2ee7630565a6b5383bfe5540ed947472
Tx public key: e87d4406d02f9638a09691fdc09aa914fc5d89969425a7923096d7b55db9d4a7
Timestamp: 1707344846 Timestamp [UCT]: 2024-02-07 22:27:26 Age [y:d:h:m:s]: 01:020:07:49:55
Block: 952635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275537 RingCT/type: yes/0
Extra: 01e87d4406d02f9638a09691fdc09aa914fc5d89969425a7923096d7b55db9d4a702110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6712c12dadd1698135df962d91838d07fa98935d9a9433c916b8cfc1f153ba90 0.600000000000 1411721 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": 952645, "vin": [ { "gen": { "height": 952635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6712c12dadd1698135df962d91838d07fa98935d9a9433c916b8cfc1f153ba90" } } ], "extra": [ 1, 232, 125, 68, 6, 208, 47, 150, 56, 160, 150, 145, 253, 192, 154, 169, 20, 252, 93, 137, 150, 148, 37, 167, 146, 48, 150, 215, 181, 93, 185, 212, 167, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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