Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efca3d9ea1acd8f56631b5424eeecfeff4ffa3c1f4b392808390bbc8775b5b01

Tx prefix hash: 7d03306c6467817f8bdc280b88c7bc16f7b97e07d6dd7defbd48a7add5df36c2
Tx public key: 7f5d7d90e5a844bfb2549d3ec5a8f8bbd9ea33f55b89ec10222c85c0dc22d56f
Timestamp: 1737142309 Timestamp [UCT]: 2025-01-17 19:31:49 Age [y:d:h:m:s]: 00:300:04:07:15
Block: 1199527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212033 RingCT/type: yes/0
Extra: 017f5d7d90e5a844bfb2549d3ec5a8f8bbd9ea33f55b89ec10222c85c0dc22d56f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1af3d98be4af5ba1d284ad9e8ced5b14aaea9b1128ea6b44d6068d47125c8e6f 0.600000000000 1686158 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": 1199537, "vin": [ { "gen": { "height": 1199527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1af3d98be4af5ba1d284ad9e8ced5b14aaea9b1128ea6b44d6068d47125c8e6f" } } ], "extra": [ 1, 127, 93, 125, 144, 229, 168, 68, 191, 178, 84, 157, 62, 197, 168, 248, 187, 217, 234, 51, 245, 91, 137, 236, 16, 34, 44, 133, 192, 220, 34, 213, 111, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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