Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9492dfc37f9595c8da87f8189090be6cac90d11bfd50ce3ac9260fe65ca154a5

Tx prefix hash: 4040d71f543ec5e50ddc89c9fd2e8821ede02677fa4834b6099dcee2ba5c421c
Tx public key: 1585aefb85d4d6df8d273ede4ff6e59b9fb05e24f8b6f729eb68e9f6812c2c5e
Timestamp: 1713341113 Timestamp [UCT]: 2024-04-17 08:05:13 Age [y:d:h:m:s]: 01:049:13:31:06
Block: 1002348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296404 RingCT/type: yes/0
Extra: 011585aefb85d4d6df8d273ede4ff6e59b9fb05e24f8b6f729eb68e9f6812c2c5e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df8f6a407e1e5a5e53102125b07ac8bd0a1081e74c8818ba3824067c6cfd79e2 0.600000000000 1462864 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": 1002358, "vin": [ { "gen": { "height": 1002348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df8f6a407e1e5a5e53102125b07ac8bd0a1081e74c8818ba3824067c6cfd79e2" } } ], "extra": [ 1, 21, 133, 174, 251, 133, 212, 214, 223, 141, 39, 62, 222, 79, 246, 229, 155, 159, 176, 94, 36, 248, 182, 247, 41, 235, 104, 233, 246, 129, 44, 44, 94, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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