Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 336d9af95dc365c7cbc6bd4554a444a243cb71e75cfb4eb4d6089d99733c4c2d

Tx prefix hash: e4417f60a5842e9bf63b12348f070a7aa2c8dc627493c554f8d57c3ae2439652
Tx public key: 9594d6f1ae9b4a6e99e8460cbbfce0363bb7753574fe7bd1dce4b3e74241ba0a
Timestamp: 1739297142 Timestamp [UCT]: 2025-02-11 18:05:42 Age [y:d:h:m:s]: 00:324:04:01:22
Block: 1217105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229496 RingCT/type: yes/0
Extra: 019594d6f1ae9b4a6e99e8460cbbfce0363bb7753574fe7bd1dce4b3e74241ba0a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 294a808dc5b931f9f7aee5235692cd7ee9eb68387b38f87f0b4a5977d7d2bc4b 0.600000000000 1703914 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": 1217115, "vin": [ { "gen": { "height": 1217105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "294a808dc5b931f9f7aee5235692cd7ee9eb68387b38f87f0b4a5977d7d2bc4b" } } ], "extra": [ 1, 149, 148, 214, 241, 174, 155, 74, 110, 153, 232, 70, 12, 187, 252, 224, 54, 59, 183, 117, 53, 116, 254, 123, 209, 220, 228, 179, 231, 66, 65, 186, 10, 2, 17, 0, 0, 0, 7, 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