Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f9a0869e34e47fe2fc37342e19d20b6b6b069806c8b98fc5fa6f85f24d141fd

Tx prefix hash: 56c4988ce50ecfdbaf1f07e3c7bbd9c9d15563734f51bd42c49e0d6398e01cf4
Tx public key: f323cac758bed46e13b701bcd0db000e5de71075a85594d2ab3b1fe766c5d495
Timestamp: 1745870615 Timestamp [UCT]: 2025-04-28 20:03:35 Age [y:d:h:m:s]: 00:012:17:45:25
Block: 1271525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9108 RingCT/type: yes/0
Extra: 01f323cac758bed46e13b701bcd0db000e5de71075a85594d2ab3b1fe766c5d49502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4acd2cbe7762e0f5b6c25d5bf945e182ae2c53b4b676216684fc690e18e419bf 0.600000000000 1758788 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": 1271535, "vin": [ { "gen": { "height": 1271525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4acd2cbe7762e0f5b6c25d5bf945e182ae2c53b4b676216684fc690e18e419bf" } } ], "extra": [ 1, 243, 35, 202, 199, 88, 190, 212, 110, 19, 183, 1, 188, 208, 219, 0, 14, 93, 231, 16, 117, 168, 85, 148, 210, 171, 59, 31, 231, 102, 197, 212, 149, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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