Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1db8d52861697e4ec82fd4a8778ef0650e8d33496cf151c8a2d081765c0bec1

Tx prefix hash: 966a3cc7850480eceade56cbcfc699b589cf3f9cec752d2aa69621c90c0edc25
Tx public key: 15f89f6bf159f6403314b6d4c7b7012467b2352c2f91eac5caef3dfdd3c709e4
Timestamp: 1707155891 Timestamp [UCT]: 2024-02-05 17:58:11 Age [y:d:h:m:s]: 01:084:13:46:17
Block: 951061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321524 RingCT/type: yes/0
Extra: 0115f89f6bf159f6403314b6d4c7b7012467b2352c2f91eac5caef3dfdd3c709e402110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afe14cfe4755b46f0b8333cd336bc1b0418db49f614452bd5fc7447a709dc7e0 0.600000000000 1409773 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": 951071, "vin": [ { "gen": { "height": 951061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afe14cfe4755b46f0b8333cd336bc1b0418db49f614452bd5fc7447a709dc7e0" } } ], "extra": [ 1, 21, 248, 159, 107, 241, 89, 246, 64, 51, 20, 182, 212, 199, 183, 1, 36, 103, 178, 53, 44, 47, 145, 234, 197, 202, 239, 61, 253, 211, 199, 9, 228, 2, 17, 0, 0, 0, 8, 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