Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1927c6ea155c61f43fc115a0bd02b6576e85788f7097a871f64f35da67883467

Tx prefix hash: 57a860d408dbe269cbb96f01616c76c8eba35f0a99d08cffe40c53776daa9acf
Tx public key: f694a0c0cee2196ba74cb1f6e2c041f39b3c67cb870637402bc37d79656dc94b
Timestamp: 1710587620 Timestamp [UCT]: 2024-03-16 11:13:40 Age [y:d:h:m:s]: 01:237:16:00:49
Block: 979538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428546 RingCT/type: yes/0
Extra: 01f694a0c0cee2196ba74cb1f6e2c041f39b3c67cb870637402bc37d79656dc94b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f90643abd3cbda04081cfdda4d71c18fc284a9563504b25f56630bc8817948e 0.600000000000 1439573 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": 979548, "vin": [ { "gen": { "height": 979538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f90643abd3cbda04081cfdda4d71c18fc284a9563504b25f56630bc8817948e" } } ], "extra": [ 1, 246, 148, 160, 192, 206, 226, 25, 107, 167, 76, 177, 246, 226, 192, 65, 243, 155, 60, 103, 203, 135, 6, 55, 64, 43, 195, 125, 121, 101, 109, 201, 75, 2, 17, 0, 0, 0, 2, 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