Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41b99ae08f9960bb7df903c7adddcb80bfb6f98c5d7326e2aaae92beebfdd680

Tx prefix hash: 1ae6739dde4d1b5c1b3ce0884affa704d143609f098273d7070c6965bf277999
Tx public key: 07ffbca0fbbfa0c828ab0c9e5ac6728df995be7eb8ee4f95b999d8b07269c580
Timestamp: 1724020213 Timestamp [UCT]: 2024-08-18 22:30:13 Age [y:d:h:m:s]: 00:144:20:07:34
Block: 1090892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103602 RingCT/type: yes/0
Extra: 0107ffbca0fbbfa0c828ab0c9e5ac6728df995be7eb8ee4f95b999d8b07269c580021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44306b74642e6cf28638fc86e06549c5e96cdd3dfd7760761e79d6cd67ad2eea 0.600000000000 1565517 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": 1090902, "vin": [ { "gen": { "height": 1090892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44306b74642e6cf28638fc86e06549c5e96cdd3dfd7760761e79d6cd67ad2eea" } } ], "extra": [ 1, 7, 255, 188, 160, 251, 191, 160, 200, 40, 171, 12, 158, 90, 198, 114, 141, 249, 149, 190, 126, 184, 238, 79, 149, 185, 153, 216, 176, 114, 105, 197, 128, 2, 17, 0, 0, 0, 1, 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