Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4e15974e9465bb56baf54806933ee70cfac4ffa8fc0cab3cb9c7ead6d9e1673

Tx prefix hash: 642b20dab7450c3748faa5df7032d1a273d405929ebf9ff9759ee839adb53f3a
Tx public key: 7ab9299d1a289e35b042433e1ff03aca7c0fd71f924f7376bd6f640c1a495ff8
Timestamp: 1709086111 Timestamp [UCT]: 2024-02-28 02:08:31 Age [y:d:h:m:s]: 01:260:22:24:20
Block: 967079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445226 RingCT/type: yes/0
Extra: 017ab9299d1a289e35b042433e1ff03aca7c0fd71f924f7376bd6f640c1a495ff802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99da61f4aaba762ecb0ebcad8f6decd4d8a0a148b23b518ffb0bce7577c763c7 0.600000000000 1426850 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": 967089, "vin": [ { "gen": { "height": 967079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99da61f4aaba762ecb0ebcad8f6decd4d8a0a148b23b518ffb0bce7577c763c7" } } ], "extra": [ 1, 122, 185, 41, 157, 26, 40, 158, 53, 176, 66, 67, 62, 31, 240, 58, 202, 124, 15, 215, 31, 146, 79, 115, 118, 189, 111, 100, 12, 26, 73, 95, 248, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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