Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77285acc17e50a0ebbe62f7f2184432e3562277232f80c79f84b7f4984b735f2

Tx prefix hash: b4cc523047ab657255d9d68f05fa3318aa0e8f3149103a64519ce6b101027bcc
Tx public key: 9cd9c36456ad0cd9c6977a8a4bcda3e98b5782c58181f3ecc13c1124afed76c5
Timestamp: 1712879792 Timestamp [UCT]: 2024-04-11 23:56:32 Age [y:d:h:m:s]: 00:320:14:00:20
Block: 998500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229197 RingCT/type: yes/0
Extra: 019cd9c36456ad0cd9c6977a8a4bcda3e98b5782c58181f3ecc13c1124afed76c502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80a79edcba8d2d6706c9db556519913374d2ba7c53ccba049e4a9e7bde6a0f6b 0.600000000000 1458952 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": 998510, "vin": [ { "gen": { "height": 998500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80a79edcba8d2d6706c9db556519913374d2ba7c53ccba049e4a9e7bde6a0f6b" } } ], "extra": [ 1, 156, 217, 195, 100, 86, 173, 12, 217, 198, 151, 122, 138, 75, 205, 163, 233, 139, 87, 130, 197, 129, 129, 243, 236, 193, 60, 17, 36, 175, 237, 118, 197, 2, 17, 0, 0, 0, 4, 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