Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be1e906248f399045c3028e52b66275ac8b3538c9f7ce83100d24d1e3d14175d

Tx prefix hash: 445cf0dc91b0f2effd9f8a3c4fae4c1d00189edccd3032a024076f8113b02a05
Tx public key: b83b7714d0b20362344c1746dddcfd1f985f0f7be01278788af460218a0f916b
Timestamp: 1712923292 Timestamp [UCT]: 2024-04-12 12:01:32 Age [y:d:h:m:s]: 00:360:06:37:30
Block: 998868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257573 RingCT/type: yes/0
Extra: 01b83b7714d0b20362344c1746dddcfd1f985f0f7be01278788af460218a0f916b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01cde57540a02cfaf9856a163d9f8c4587583a33a9093c39b1381f306800571a 0.600000000000 1459334 of 15

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": 998878, "vin": [ { "gen": { "height": 998868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01cde57540a02cfaf9856a163d9f8c4587583a33a9093c39b1381f306800571a" } } ], "extra": [ 1, 184, 59, 119, 20, 208, 178, 3, 98, 52, 76, 23, 70, 221, 220, 253, 31, 152, 95, 15, 123, 224, 18, 120, 120, 138, 244, 96, 33, 138, 15, 145, 107, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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