Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7148de89e4c1577dce5f3cd67758a06b296811e3326c172f8e4e6222eef5177e

Tx prefix hash: 5726fb5ca2035c2c5c56dcec6799e99c181c97c98fa2a2aed7663a76488989f8
Tx public key: 27e4dc14fe2d1f77ea8804e2af4f6938a2e248bd1588a79042e01c958ed0f813
Timestamp: 1731747792 Timestamp [UCT]: 2024-11-16 09:03:12 Age [y:d:h:m:s]: 00:136:15:13:42
Block: 1154862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97457 RingCT/type: yes/0
Extra: 0127e4dc14fe2d1f77ea8804e2af4f6938a2e248bd1588a79042e01c958ed0f813021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a67f27ca11a1a64ddb9b4d8c4edfd5b90fa3f563bdd99bdf995cb389e5a2f06 0.600000000000 1640475 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": 1154872, "vin": [ { "gen": { "height": 1154862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a67f27ca11a1a64ddb9b4d8c4edfd5b90fa3f563bdd99bdf995cb389e5a2f06" } } ], "extra": [ 1, 39, 228, 220, 20, 254, 45, 31, 119, 234, 136, 4, 226, 175, 79, 105, 56, 162, 226, 72, 189, 21, 136, 167, 144, 66, 224, 28, 149, 142, 208, 248, 19, 2, 17, 0, 0, 0, 5, 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