Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46b5205e63ed735a5990dfe60e4beca6762afdf326d5ded3485328b88bf123ff

Tx prefix hash: bcf1d7d79fcafed3a85afe94afcdd023c6b44f5b237b79a27288a030c7c0b38f
Tx public key: bb16fd284e6a8ea8da11909d29dea892db8a12cd7a3d435d698371bb296ce562
Timestamp: 1577895608 Timestamp [UCT]: 2020-01-01 16:20:08 Age [y:d:h:m:s]: 04:362:21:12:38
Block: 36430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148603 RingCT/type: yes/0
Extra: 01bb16fd284e6a8ea8da11909d29dea892db8a12cd7a3d435d698371bb296ce5620211000000068a2ee0d9000000000000000000

1 output(s) for total of 464.828919543000 dcy

stealth address amount amount idx
00: df558cb51815d9448021dba9343a0159dacbf780363420533c33c5adfe9fb6d7 464.828919543000 61723 of 0

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": 36440, "vin": [ { "gen": { "height": 36430 } } ], "vout": [ { "amount": 464828919543, "target": { "key": "df558cb51815d9448021dba9343a0159dacbf780363420533c33c5adfe9fb6d7" } } ], "extra": [ 1, 187, 22, 253, 40, 78, 106, 142, 168, 218, 17, 144, 157, 41, 222, 168, 146, 219, 138, 18, 205, 122, 61, 67, 93, 105, 131, 113, 187, 41, 108, 229, 98, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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