Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98a577b8c2b73e70e09245b453845323dbd1534b183b14d485c18b00d0fe266f

Tx prefix hash: d5f20cf05b04771e4e820182e6a059da6f36dda7af292fde417c61e19070b4f7
Tx public key: 4b179f834443c66574c5ae23192b6dd0d948d59dbe5ee8388610784618f4bb1c
Timestamp: 1730830340 Timestamp [UCT]: 2024-11-05 18:12:20 Age [y:d:h:m:s]: 00:145:11:06:45
Block: 1147253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103793 RingCT/type: yes/0
Extra: 014b179f834443c66574c5ae23192b6dd0d948d59dbe5ee8388610784618f4bb1c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f6fc925ddfab9699e2aa01b3d2a2077cc15b349ae4f464107efadb66a1ddf2c 0.600000000000 1631948 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": 1147263, "vin": [ { "gen": { "height": 1147253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f6fc925ddfab9699e2aa01b3d2a2077cc15b349ae4f464107efadb66a1ddf2c" } } ], "extra": [ 1, 75, 23, 159, 131, 68, 67, 198, 101, 116, 197, 174, 35, 25, 43, 109, 208, 217, 72, 213, 157, 190, 94, 232, 56, 134, 16, 120, 70, 24, 244, 187, 28, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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