Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49063ccaab61f02e7e0d18c5cc01c06e4183c77badb35402a568a1973d8b3e3a

Tx prefix hash: 29d7ce3344c72dc516bfd10a1911fdf451bf4ae3cda63e395d391676b680585c
Tx public key: 6f7bde5f8520c43471b13644a1c2ae5d57af08f9b0f8aeb010ae7c7f996899d8
Timestamp: 1703945370 Timestamp [UCT]: 2023-12-30 14:09:30 Age [y:d:h:m:s]: 01:025:01:06:51
Block: 924464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279185 RingCT/type: yes/0
Extra: 016f7bde5f8520c43471b13644a1c2ae5d57af08f9b0f8aeb010ae7c7f996899d8021100000005ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3afc5e5469a3f8a7e55ec036525c9e0b0a4d439191989e6b5564db780c735d0f 0.600000000000 1382214 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": 924474, "vin": [ { "gen": { "height": 924464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3afc5e5469a3f8a7e55ec036525c9e0b0a4d439191989e6b5564db780c735d0f" } } ], "extra": [ 1, 111, 123, 222, 95, 133, 32, 196, 52, 113, 177, 54, 68, 161, 194, 174, 93, 87, 175, 8, 249, 176, 248, 174, 176, 16, 174, 124, 127, 153, 104, 153, 216, 2, 17, 0, 0, 0, 5, 172, 50, 141, 17, 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