Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92c104c2253dc7285a8acde1e8f108baee3a1ae59789056c898d25ac1c81e206

Tx prefix hash: 4a66fbb6bb3bc38617ab6c203bd2d8f57e835b1e4f15046161612d29f8f6e2fd
Tx public key: 88e03e73f0e656378d99e448b238202665de1a2ab646e3e6f8bb830bbc81f9c4
Timestamp: 1734498774 Timestamp [UCT]: 2024-12-18 05:12:54 Age [y:d:h:m:s]: 00:338:04:57:57
Block: 1177678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239199 RingCT/type: yes/0
Extra: 0188e03e73f0e656378d99e448b238202665de1a2ab646e3e6f8bb830bbc81f9c4021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f25acf219eb31d8e4060350b7054e5672429b72a8b132df4a3b1687577750b9 0.600000000000 1664051 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": 1177688, "vin": [ { "gen": { "height": 1177678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f25acf219eb31d8e4060350b7054e5672429b72a8b132df4a3b1687577750b9" } } ], "extra": [ 1, 136, 224, 62, 115, 240, 230, 86, 55, 141, 153, 228, 72, 178, 56, 32, 38, 101, 222, 26, 42, 182, 70, 227, 230, 248, 187, 131, 11, 188, 129, 249, 196, 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