Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 224cda18bbca68259cf30c6a13efd3a15945b3711ee97ef94747d39a4cc2c6b0

Tx prefix hash: becc530459c8056f537473a1c64ef12aa268b99675b08396ea8a60768b72048c
Tx public key: 8f8579308892dc39c7900aaf958d29c79d80f5a84f464cb6c5f4bc648b71eb45
Timestamp: 1736884306 Timestamp [UCT]: 2025-01-14 19:51:46 Age [y:d:h:m:s]: 00:154:11:16:38
Block: 1197384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110111 RingCT/type: yes/0
Extra: 018f8579308892dc39c7900aaf958d29c79d80f5a84f464cb6c5f4bc648b71eb45021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 181b0c54343f9577b6023698b7d1c9402c9b6bbfb8aafcfc3a03e8fa8d8837e4 0.600000000000 1683991 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": 1197394, "vin": [ { "gen": { "height": 1197384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "181b0c54343f9577b6023698b7d1c9402c9b6bbfb8aafcfc3a03e8fa8d8837e4" } } ], "extra": [ 1, 143, 133, 121, 48, 136, 146, 220, 57, 199, 144, 10, 175, 149, 141, 41, 199, 157, 128, 245, 168, 79, 70, 76, 182, 197, 244, 188, 100, 139, 113, 235, 69, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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