Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2dfb641999cff4b8b0f59d231506efd69e68608be9e3003e27380e9b90ab426

Tx prefix hash: ce0a51e370fbb05d9e5821bffecae17ba450f8eedd96f3c0f2f4e2bbc5febc0a
Tx public key: 4cc4fe03ea0126ee3dd10f3de43ced8352be15d7699d0444129d245eb09a9ea6
Timestamp: 1734338302 Timestamp [UCT]: 2024-12-16 08:38:22 Age [y:d:h:m:s]: 00:095:23:37:23
Block: 1176334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68366 RingCT/type: yes/0
Extra: 014cc4fe03ea0126ee3dd10f3de43ced8352be15d7699d0444129d245eb09a9ea6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 756bf5f46e14a244218c630d45a7a7f42f067c4332e9baef6ec8cfae277cb263 0.600000000000 1662665 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": 1176344, "vin": [ { "gen": { "height": 1176334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756bf5f46e14a244218c630d45a7a7f42f067c4332e9baef6ec8cfae277cb263" } } ], "extra": [ 1, 76, 196, 254, 3, 234, 1, 38, 238, 61, 209, 15, 61, 228, 60, 237, 131, 82, 190, 21, 215, 105, 157, 4, 68, 18, 157, 36, 94, 176, 154, 158, 166, 2, 17, 0, 0, 0, 3, 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