Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa07b01b6cf8febf097b2a9cc1f1744fa94cdf5c6dc6282a9d609de22beaa38e

Tx prefix hash: 1ecf13ab4d7fd9aa054ba3ef5a77177e9c64801f641d4cdc12cd4f013823b2e9
Tx public key: 36730cd2a330d4613394af01db589a96eafe2ce12f8a35f422457659558af2e6
Timestamp: 1722396233 Timestamp [UCT]: 2024-07-31 03:23:53 Age [y:d:h:m:s]: 00:245:19:57:47
Block: 1077416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175588 RingCT/type: yes/0
Extra: 0136730cd2a330d4613394af01db589a96eafe2ce12f8a35f422457659558af2e6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f497575f7c97c13cd7f136c651b2cb1db4c03dc8359b72ee66dc23d4fb58bd 0.600000000000 1549963 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": 1077426, "vin": [ { "gen": { "height": 1077416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f497575f7c97c13cd7f136c651b2cb1db4c03dc8359b72ee66dc23d4fb58bd" } } ], "extra": [ 1, 54, 115, 12, 210, 163, 48, 212, 97, 51, 148, 175, 1, 219, 88, 154, 150, 234, 254, 44, 225, 47, 138, 53, 244, 34, 69, 118, 89, 85, 138, 242, 230, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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