Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d365da240dda3d1505c96362e5b7d5a0aac66bf3165753009f5a30df0ff03ec9

Tx prefix hash: c4e2b9abe6bd3d26f533df950ce64c71cc687fe9a9bc3cdb825f3c5054ce09db
Tx public key: d8cda7d2fce90f36db9f73c63fff44b003f998ea4a86c2161d459c865eb6bce8
Timestamp: 1705759871 Timestamp [UCT]: 2024-01-20 14:11:11 Age [y:d:h:m:s]: 01:317:16:51:29
Block: 939465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485926 RingCT/type: yes/0
Extra: 01d8cda7d2fce90f36db9f73c63fff44b003f998ea4a86c2161d459c865eb6bce80211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30d4fdc617b681510430e08c1e4087e8cd9439d29843f1007b6f84f6e4361789 0.600000000000 1397573 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": 939475, "vin": [ { "gen": { "height": 939465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30d4fdc617b681510430e08c1e4087e8cd9439d29843f1007b6f84f6e4361789" } } ], "extra": [ 1, 216, 205, 167, 210, 252, 233, 15, 54, 219, 159, 115, 198, 63, 255, 68, 176, 3, 249, 152, 234, 74, 134, 194, 22, 29, 69, 156, 134, 94, 182, 188, 232, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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