Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1fd377a8728e1f6fa9fb60bdf79a0cf511601c759f39581548bd6bc891b432

Tx prefix hash: 5224b743b5781a9d6310d88f16b74c587a8c59fe37baf35281a7a8fdd639e0f6
Tx public key: 5930d08e81e4defc2604cb59886314d42813fc4bc2110569215b40734e343ceb
Timestamp: 1701605806 Timestamp [UCT]: 2023-12-03 12:16:46 Age [y:d:h:m:s]: 01:082:21:10:20
Block: 905053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320351 RingCT/type: yes/0
Extra: 015930d08e81e4defc2604cb59886314d42813fc4bc2110569215b40734e343ceb021100000004faf35c9c000000000000000000

1 output(s) for total of 0.615437112000 dcy

stealth address amount amount idx
00: 3181e2bc80b3a32b4fd598354cc1ac076d95bd18d11bebd751b57f18cc1aa226 0.615437112000 1361880 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": 905063, "vin": [ { "gen": { "height": 905053 } } ], "vout": [ { "amount": 615437112, "target": { "key": "3181e2bc80b3a32b4fd598354cc1ac076d95bd18d11bebd751b57f18cc1aa226" } } ], "extra": [ 1, 89, 48, 208, 142, 129, 228, 222, 252, 38, 4, 203, 89, 136, 99, 20, 212, 40, 19, 252, 75, 194, 17, 5, 105, 33, 91, 64, 115, 78, 52, 60, 235, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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