Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d69c1cd8b7e149fcbe4e4f681b7f078f3f752f5dd77075290bdbb39c0f26763d

Tx prefix hash: cf64529229eed54ac7e2604a61ee0fec8cf3229cfa51d7e4b4f5f8c80e12ac95
Tx public key: ee9e7772f79f4bb76d6ed96a1f12ce181e3e1f6e3485bd3e38478ac761d95547
Timestamp: 1705155154 Timestamp [UCT]: 2024-01-13 14:12:34 Age [y:d:h:m:s]: 01:090:02:26:28
Block: 934473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325496 RingCT/type: yes/0
Extra: 01ee9e7772f79f4bb76d6ed96a1f12ce181e3e1f6e3485bd3e38478ac761d955470211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbb39ec167951b4fed94c8ecee718f11afd0e05cede9d3fabed56a39cc53580a 0.600000000000 1392485 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": 934483, "vin": [ { "gen": { "height": 934473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbb39ec167951b4fed94c8ecee718f11afd0e05cede9d3fabed56a39cc53580a" } } ], "extra": [ 1, 238, 158, 119, 114, 247, 159, 75, 183, 109, 110, 217, 106, 31, 18, 206, 24, 30, 62, 31, 110, 52, 133, 189, 62, 56, 71, 138, 199, 97, 217, 85, 71, 2, 17, 0, 0, 0, 7, 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