Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48c5717052ed76581f0d37d6df11a96b6357d2d6ec12223108135fd5ff546510

Tx prefix hash: 2f2a749c6fcb6ad034908701f54f151bced6e6b60f2b2f8176ee77ee63df5469
Tx public key: 638e677e91f8d6d42d59ba08022b0d70c89ed5cf6338278123831afed4bb8dac
Timestamp: 1711481155 Timestamp [UCT]: 2024-03-26 19:25:55 Age [y:d:h:m:s]: 00:288:10:10:44
Block: 986956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206439 RingCT/type: yes/0
Extra: 01638e677e91f8d6d42d59ba08022b0d70c89ed5cf6338278123831afed4bb8dac02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8caa0f81a2042282b253c2c2e5f1f9a0304d11e7ac997d0c122d5f33f65c766 0.600000000000 1447193 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": 986966, "vin": [ { "gen": { "height": 986956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8caa0f81a2042282b253c2c2e5f1f9a0304d11e7ac997d0c122d5f33f65c766" } } ], "extra": [ 1, 99, 142, 103, 126, 145, 248, 214, 212, 45, 89, 186, 8, 2, 43, 13, 112, 200, 158, 213, 207, 99, 56, 39, 129, 35, 131, 26, 254, 212, 187, 141, 172, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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