Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8785197fb5ba8eb7b70d8661e6288076269cedbeafb34613f840e6f9e804764

Tx prefix hash: ffe46683e417194fdffb82536c4afb70543d45606a5f488fe3335f591d8d04bc
Tx public key: 84754329323711a3c49b5f232b0ce8e64c8d0ec5d4933b8e5d4d7241ce163cf6
Timestamp: 1674652161 Timestamp [UCT]: 2023-01-25 13:09:21 Age [y:d:h:m:s]: 02:124:23:14:55
Block: 682480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 611005 RingCT/type: yes/0
Extra: 0184754329323711a3c49b5f232b0ce8e64c8d0ec5d4933b8e5d4d7241ce163cf602110000000252542ceb000000000000000000

1 output(s) for total of 3.362485251000 dcy

stealth address amount amount idx
00: 9d80983d086ffd8ee6349e7b0627cf26763956078e7dfd474c00e30a05a71ecb 3.362485251000 1124605 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": 682490, "vin": [ { "gen": { "height": 682480 } } ], "vout": [ { "amount": 3362485251, "target": { "key": "9d80983d086ffd8ee6349e7b0627cf26763956078e7dfd474c00e30a05a71ecb" } } ], "extra": [ 1, 132, 117, 67, 41, 50, 55, 17, 163, 196, 155, 95, 35, 43, 12, 232, 230, 76, 141, 14, 197, 212, 147, 59, 142, 93, 77, 114, 65, 206, 22, 60, 246, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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