Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30b2fee3d226278f2ac6c8423fd90c58b95e63bdd362de75f9f2120352060a88

Tx prefix hash: c6cde2ba249e87e10ebd64d58ead2b9481678919bfa6778bfe8d335e14a2002c
Tx public key: b79cddad7e1eabe177e84358ef1e8bc6d85a85139ae83ce2d2e2044ec98f1a69
Timestamp: 1628250514 Timestamp [UCT]: 2021-08-06 11:48:34 Age [y:d:h:m:s]: 03:140:11:40:32
Block: 308445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 873335 RingCT/type: yes/0
Extra: 01b79cddad7e1eabe177e84358ef1e8bc6d85a85139ae83ce2d2e2044ec98f1a6902110000000801f1e57f000000000000000000

1 output(s) for total of 58.344734728000 dcy

stealth address amount amount idx
00: 39ab073573b43dcfccfa3cf5877e6ca66ba19d91757ca8234c01ee2450f2d251 58.344734728000 642886 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": 308455, "vin": [ { "gen": { "height": 308445 } } ], "vout": [ { "amount": 58344734728, "target": { "key": "39ab073573b43dcfccfa3cf5877e6ca66ba19d91757ca8234c01ee2450f2d251" } } ], "extra": [ 1, 183, 156, 221, 173, 126, 30, 171, 225, 119, 232, 67, 88, 239, 30, 139, 198, 216, 90, 133, 19, 154, 232, 60, 226, 210, 226, 4, 78, 201, 143, 26, 105, 2, 17, 0, 0, 0, 8, 1, 241, 229, 127, 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