Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8aff0f46d2a639279f4cbdc1959f3b36f8bd7f6cacdbb5ca616d3811b6d429e

Tx prefix hash: b6f644d83d6e832da515c13d65e1fd2f6cbb1e2ff8c89d8d11adb2fb81d6d525
Tx public key: 713ebb2ef6ee730c87389e5a608386142f9422dce8386d6b8b6e2be6da782d2d
Timestamp: 1699105094 Timestamp [UCT]: 2023-11-04 13:38:14 Age [y:d:h:m:s]: 01:076:19:18:05
Block: 884575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316029 RingCT/type: yes/0
Extra: 01713ebb2ef6ee730c87389e5a608386142f9422dce8386d6b8b6e2be6da782d2d02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.719508330000 dcy

stealth address amount amount idx
00: 9285f6ff58b2bb85551866c5def77fed62a67cbb54dc773a8af3d5deeef4011d 0.719508330000 1340320 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": 884585, "vin": [ { "gen": { "height": 884575 } } ], "vout": [ { "amount": 719508330, "target": { "key": "9285f6ff58b2bb85551866c5def77fed62a67cbb54dc773a8af3d5deeef4011d" } } ], "extra": [ 1, 113, 62, 187, 46, 246, 238, 115, 12, 135, 56, 158, 90, 96, 131, 134, 20, 47, 148, 34, 220, 232, 56, 109, 107, 139, 110, 43, 230, 218, 120, 45, 45, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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