Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb91d3565d7a094933b8a9d09eaf25d389f6da8f5267fcaffa3264ec55414386

Tx prefix hash: 144cc1c9818d82a2a133d8311a64313279fcdac0f232d8dee1d830b41896407a
Tx public key: bf6c09b52460f33b565f018f4caf1598110d155ad947b36e15dd7e226962c2f2
Timestamp: 1699541808 Timestamp [UCT]: 2023-11-09 14:56:48 Age [y:d:h:m:s]: 01:211:12:18:07
Block: 887955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412394 RingCT/type: yes/0
Extra: 01bf6c09b52460f33b565f018f4caf1598110d155ad947b36e15dd7e226962c2f202110000000333af99f4000000000000000000

1 output(s) for total of 0.701191234000 dcy

stealth address amount amount idx
00: 3913d1c1ba7b89d2a3c0aa63be492a77aede0d40c0535d12af6abddd21861aa5 0.701191234000 1343868 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": 887965, "vin": [ { "gen": { "height": 887955 } } ], "vout": [ { "amount": 701191234, "target": { "key": "3913d1c1ba7b89d2a3c0aa63be492a77aede0d40c0535d12af6abddd21861aa5" } } ], "extra": [ 1, 191, 108, 9, 181, 36, 96, 243, 59, 86, 95, 1, 143, 76, 175, 21, 152, 17, 13, 21, 90, 217, 71, 179, 110, 21, 221, 126, 34, 105, 98, 194, 242, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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