Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f338f64d5433a9b86a5970bbafdad1e35c32287b4489dd6ca2ad564f5a563f

Tx prefix hash: 54886fdd4613f0d8cf828fd1eff3194495e7851d913a435b5f2172f08ac607b6
Tx public key: c8a1c8a5dd4c42f50e755d13acdc03d546564027a071644d925f0c4e018ce646
Timestamp: 1723720238 Timestamp [UCT]: 2024-08-15 11:10:38 Age [y:d:h:m:s]: 00:239:04:02:41
Block: 1088400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170818 RingCT/type: yes/0
Extra: 01c8a1c8a5dd4c42f50e755d13acdc03d546564027a071644d925f0c4e018ce64602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 849443f556dfd58badd9f0959b27f6e09165c201d9de05d1605b1ab186b31fe3 0.600000000000 1563015 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": 1088410, "vin": [ { "gen": { "height": 1088400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "849443f556dfd58badd9f0959b27f6e09165c201d9de05d1605b1ab186b31fe3" } } ], "extra": [ 1, 200, 161, 200, 165, 221, 76, 66, 245, 14, 117, 93, 19, 172, 220, 3, 213, 70, 86, 64, 39, 160, 113, 100, 77, 146, 95, 12, 78, 1, 140, 230, 70, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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