Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28acb092203ba165ecc365b0edfc5f9e498ad0acc4f85f8d8a4e5fe3225774d6

Tx prefix hash: 56ffff8743ead6e95a8ef4aa66c428ced6fc6d4df8e75c8c3a1839af862f0c28
Tx public key: 9f7fe0d816746ff25a05c6621d382e698cebb917261b3a6a01fb15e545e84d77
Timestamp: 1750742718 Timestamp [UCT]: 2025-06-24 05:25:18 Age [y:d:h:m:s]: 00:144:23:05:47
Block: 1311598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101541 RingCT/type: yes/0
Extra: 019f7fe0d816746ff25a05c6621d382e698cebb917261b3a6a01fb15e545e84d77021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d02f7938d50f5a7c6681b61d3106a079ca2a71e1e6e332d4bab34f0adf3d5b 0.600000000000 1799225 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": 1311608, "vin": [ { "gen": { "height": 1311598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d02f7938d50f5a7c6681b61d3106a079ca2a71e1e6e332d4bab34f0adf3d5b" } } ], "extra": [ 1, 159, 127, 224, 216, 22, 116, 111, 242, 90, 5, 198, 98, 29, 56, 46, 105, 140, 235, 185, 23, 38, 27, 58, 106, 1, 251, 21, 229, 69, 232, 77, 119, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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