Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e8dcf4989de2afa42bb474baa4600fa0c55a0b2346a618d3bd85ac01a0c4e9a

Tx prefix hash: ddf252ecad24e54da27fd734af79db018be73e3f356f73143aebd1bd7ee398ab
Tx public key: b53fb7de3f82dae5af16a9ca7a979332098043cb67130fa2cef105a7eb5bd474
Timestamp: 1704084961 Timestamp [UCT]: 2024-01-01 04:56:01 Age [y:d:h:m:s]: 01:324:23:09:01
Block: 925607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491085 RingCT/type: yes/0
Extra: 01b53fb7de3f82dae5af16a9ca7a979332098043cb67130fa2cef105a7eb5bd4740211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d596fdeaf1f06e06b476dce2d6b5a2ce1486a1c2e8b57937443e8a5f21b88abd 0.600000000000 1383371 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": 925617, "vin": [ { "gen": { "height": 925607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d596fdeaf1f06e06b476dce2d6b5a2ce1486a1c2e8b57937443e8a5f21b88abd" } } ], "extra": [ 1, 181, 63, 183, 222, 63, 130, 218, 229, 175, 22, 169, 202, 122, 151, 147, 50, 9, 128, 67, 203, 103, 19, 15, 162, 206, 241, 5, 167, 235, 91, 212, 116, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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