Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 180cd9e287c82b96a5fdb9e4ecaea9fa5f9423fe65985c4317b7dfead3d71e76

Tx prefix hash: 019aecf1720055ebc5d20c2160ed5a6785739d0496cd25aa26e52de1d8eed93b
Tx public key: 409662f71f1829f819caa62f6b44ad74e5e170d643410d76682f384a5116fb3b
Timestamp: 1718585160 Timestamp [UCT]: 2024-06-17 00:46:00 Age [y:d:h:m:s]: 00:221:20:39:27
Block: 1045841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158697 RingCT/type: yes/0
Extra: 01409662f71f1829f819caa62f6b44ad74e5e170d643410d76682f384a5116fb3b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abae88d4e011b48eaf1d086a5fa1c4dea42ab7fe42ec224aa3691b29c29c5513 0.600000000000 1515532 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": 1045851, "vin": [ { "gen": { "height": 1045841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abae88d4e011b48eaf1d086a5fa1c4dea42ab7fe42ec224aa3691b29c29c5513" } } ], "extra": [ 1, 64, 150, 98, 247, 31, 24, 41, 248, 25, 202, 166, 47, 107, 68, 173, 116, 229, 225, 112, 214, 67, 65, 13, 118, 104, 47, 56, 74, 81, 22, 251, 59, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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