Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3e9d079e95c6fc6311d8d2e827064f065cb8dba73198202b66a22e670f9964

Tx prefix hash: 657cb1d8bcf173f05fd2d605f2357d0c4b200ee471d698f230ad308ed13050ee
Tx public key: 6db3eead80fc95c0e2ae20d914c63c7e006a7da83ad4a3e0041ec2639ed1022b
Timestamp: 1672750547 Timestamp [UCT]: 2023-01-03 12:55:47 Age [y:d:h:m:s]: 01:334:01:41:30
Block: 666696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499782 RingCT/type: yes/0
Extra: 016db3eead80fc95c0e2ae20d914c63c7e006a7da83ad4a3e0041ec2639ed1022b021100000002272bcc39000000000000000000

1 output(s) for total of 3.792794874000 dcy

stealth address amount amount idx
00: aa29ed9f8a0ca628b86b799024d86c235086bd236fccc01180153723e1715153 3.792794874000 1107833 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": 666706, "vin": [ { "gen": { "height": 666696 } } ], "vout": [ { "amount": 3792794874, "target": { "key": "aa29ed9f8a0ca628b86b799024d86c235086bd236fccc01180153723e1715153" } } ], "extra": [ 1, 109, 179, 238, 173, 128, 252, 149, 192, 226, 174, 32, 217, 20, 198, 60, 126, 0, 106, 125, 168, 58, 212, 163, 224, 4, 30, 194, 99, 158, 209, 2, 43, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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