Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e49c3503267810bf07ddb679c0a0b7ec279922784e3a29c3e2785e015fe7400

Tx prefix hash: 6f8504b09900c74beaa20a3900e154c5e531ea3c7825ede554c2c4eb84be09cc
Tx public key: 05543d8647222e6276d2d5d88ec35ef45debe80b4712f33960a0d34a401e3e32
Timestamp: 1701598150 Timestamp [UCT]: 2023-12-03 10:09:10 Age [y:d:h:m:s]: 01:082:06:17:55
Block: 904994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319904 RingCT/type: yes/0
Extra: 0105543d8647222e6276d2d5d88ec35ef45debe80b4712f33960a0d34a401e3e3202110000000975e3f0e9000000000000000000

1 output(s) for total of 0.615714205000 dcy

stealth address amount amount idx
00: 48ff668e74e0db5a63f0c8a471d5cec4f1450392e924da625fe3c127445b10cd 0.615714205000 1361815 of 0

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": 905004, "vin": [ { "gen": { "height": 904994 } } ], "vout": [ { "amount": 615714205, "target": { "key": "48ff668e74e0db5a63f0c8a471d5cec4f1450392e924da625fe3c127445b10cd" } } ], "extra": [ 1, 5, 84, 61, 134, 71, 34, 46, 98, 118, 210, 213, 216, 142, 195, 94, 244, 93, 235, 232, 11, 71, 18, 243, 57, 96, 160, 211, 74, 64, 30, 62, 50, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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