Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b926f4e5ef9a8efb6f4d85ae299090cfbf81a40f15115173f21c27ec6e2049

Tx prefix hash: d3690f84f849b67f6fbec4ad5310b6a413d8abaee82ed0183a5cd395ef899776
Tx public key: 3fe81972a0c55736e648581a0462e97c03bef7f8b65b5a99a0901ac38bdfb01f
Timestamp: 1698513920 Timestamp [UCT]: 2023-10-28 17:25:20 Age [y:d:h:m:s]: 02:057:00:14:50
Block: 879642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560370 RingCT/type: yes/0
Extra: 013fe81972a0c55736e648581a0462e97c03bef7f8b65b5a99a0901ac38bdfb01f021100000003faf35c9c000000000000000000

1 output(s) for total of 0.747103740000 dcy

stealth address amount amount idx
00: 41922c0b9af89948a664a5ee61a2cd47698803f35427fa4317dcf253b9467af4 0.747103740000 1335176 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": 879652, "vin": [ { "gen": { "height": 879642 } } ], "vout": [ { "amount": 747103740, "target": { "key": "41922c0b9af89948a664a5ee61a2cd47698803f35427fa4317dcf253b9467af4" } } ], "extra": [ 1, 63, 232, 25, 114, 160, 197, 87, 54, 230, 72, 88, 26, 4, 98, 233, 124, 3, 190, 247, 248, 182, 91, 90, 153, 160, 144, 26, 195, 139, 223, 176, 31, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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