Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 266a3f57b2d5a94054840aafaae4f48f8e9065b1aa045c88bf27cbd93198061e

Tx prefix hash: 3fb44993db75f8ed613db1bdce6e3fc2ab610fc06128242f393b81a538ee6847
Tx public key: d4d7de8bc3bf089b72b65e718b3fe2b9d2753059c145701d3bda34a03e2178e1
Timestamp: 1745652784 Timestamp [UCT]: 2025-04-26 07:33:04 Age [y:d:h:m:s]: 00:012:07:14:41
Block: 1269714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8798 RingCT/type: yes/0
Extra: 01d4d7de8bc3bf089b72b65e718b3fe2b9d2753059c145701d3bda34a03e2178e102110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cea4e7c2da44732ade73148691b8ae75947897e53a74914dff8811b8d9581793 0.600000000000 1756953 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": 1269724, "vin": [ { "gen": { "height": 1269714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cea4e7c2da44732ade73148691b8ae75947897e53a74914dff8811b8d9581793" } } ], "extra": [ 1, 212, 215, 222, 139, 195, 191, 8, 155, 114, 182, 94, 113, 139, 63, 226, 185, 210, 117, 48, 89, 193, 69, 112, 29, 59, 218, 52, 160, 62, 33, 120, 225, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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