Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2f287bdb3223e13409100094b28bbb290fc813c6ade6341e21f84e98a0b4c2d

Tx prefix hash: 55415acf581ebb154400f6fb3f8dcb4296af66821e1c3718abe806cb17ff01c5
Tx public key: 1d49b426f8c4bb9a1cad253e98e419b3f33e22128299169c8d2b67b0aa32fb9c
Timestamp: 1732412746 Timestamp [UCT]: 2024-11-24 01:45:46 Age [y:d:h:m:s]: 00:351:23:29:07
Block: 1160373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249084 RingCT/type: yes/0
Extra: 011d49b426f8c4bb9a1cad253e98e419b3f33e22128299169c8d2b67b0aa32fb9c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 143872a75048e4a2c7b1a5e8fe75758e01cdee4d7664e79dc5e4ed0d614e7cf0 0.600000000000 1646018 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": 1160383, "vin": [ { "gen": { "height": 1160373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "143872a75048e4a2c7b1a5e8fe75758e01cdee4d7664e79dc5e4ed0d614e7cf0" } } ], "extra": [ 1, 29, 73, 180, 38, 248, 196, 187, 154, 28, 173, 37, 62, 152, 228, 25, 179, 243, 62, 34, 18, 130, 153, 22, 156, 141, 43, 103, 176, 170, 50, 251, 156, 2, 17, 0, 0, 0, 3, 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