Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf79b899650918ab7fa953e889b438a9938b7665f524e2f0da75d9c51488ca0

Tx prefix hash: a167e498cc0e3b37ef0048fb7ee0642cf528c8712e59194c65fd84463195b4f3
Tx public key: 5a67ca82ba1f117f31e8730d1a0116461ae8a3ec29c5b586c64353be90a53503
Timestamp: 1734555639 Timestamp [UCT]: 2024-12-18 21:00:39 Age [y:d:h:m:s]: 00:021:05:27:45
Block: 1178146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15157 RingCT/type: yes/0
Extra: 015a67ca82ba1f117f31e8730d1a0116461ae8a3ec29c5b586c64353be90a53503021100000016007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea9017812c23a6bc46ab08c2eb8ff1e0b24886d6b253a860c44b9cf804cdc6d 0.600000000000 1664531 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": 1178156, "vin": [ { "gen": { "height": 1178146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea9017812c23a6bc46ab08c2eb8ff1e0b24886d6b253a860c44b9cf804cdc6d" } } ], "extra": [ 1, 90, 103, 202, 130, 186, 31, 17, 127, 49, 232, 115, 13, 26, 1, 22, 70, 26, 232, 163, 236, 41, 197, 181, 134, 198, 67, 83, 190, 144, 165, 53, 3, 2, 17, 0, 0, 0, 22, 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