Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7095cc5481685a1a0e01880245d710420cba4af761c8a40f9dadb72cccf6321

Tx prefix hash: f4c7fd850bddf03e3f19cb6bcbd3379b42122b196c18c916eb56982bfffe1de5
Tx public key: 4537a8fa3e1a32a5056564880e9d5cf284f23fc0a6d4497effa3d92cccf6fc21
Timestamp: 1725860490 Timestamp [UCT]: 2024-09-09 05:41:30 Age [y:d:h:m:s]: 00:250:23:56:53
Block: 1106150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179253 RingCT/type: yes/0
Extra: 014537a8fa3e1a32a5056564880e9d5cf284f23fc0a6d4497effa3d92cccf6fc2102110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 474e1eaf5a763e58179018187a99d90d0f9412db586cfe78fe323c0de59def5a 0.600000000000 1583741 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": 1106160, "vin": [ { "gen": { "height": 1106150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "474e1eaf5a763e58179018187a99d90d0f9412db586cfe78fe323c0de59def5a" } } ], "extra": [ 1, 69, 55, 168, 250, 62, 26, 50, 165, 5, 101, 100, 136, 14, 157, 92, 242, 132, 242, 63, 192, 166, 212, 73, 126, 255, 163, 217, 44, 204, 246, 252, 33, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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