Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 450a988434c3d742e7eaefae05d58c76dce55a61483345587bf8c6ceb38c1e05

Tx prefix hash: 8bc72d9fcaa3419e4fc74af151f301c1428aff229d542b9aa7c2a7cdfea19032
Tx public key: 4fe06cbbfa25d1b9b2317002c8cb8b4366022267f535a9637b93e136dfba6b23
Timestamp: 1712031281 Timestamp [UCT]: 2024-04-02 04:14:41 Age [y:d:h:m:s]: 00:329:13:31:16
Block: 991454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235635 RingCT/type: yes/0
Extra: 014fe06cbbfa25d1b9b2317002c8cb8b4366022267f535a9637b93e136dfba6b230211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b15c1a7a1d2985901824e32e0a4bfa67642d2ae9a434d1ecf4cfce6a43a35530 0.600000000000 1451790 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": 991464, "vin": [ { "gen": { "height": 991454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b15c1a7a1d2985901824e32e0a4bfa67642d2ae9a434d1ecf4cfce6a43a35530" } } ], "extra": [ 1, 79, 224, 108, 187, 250, 37, 209, 185, 178, 49, 112, 2, 200, 203, 139, 67, 102, 2, 34, 103, 245, 53, 169, 99, 123, 147, 225, 54, 223, 186, 107, 35, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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