Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9f1d3b4d1638d4d7fa8f7b4577eb246dc71f07d1c7a2b1a9c129ce0557f2ab1

Tx prefix hash: fb56dcea8a16a4e9782a0b4d847464b083be266c95e82e320da166c24770998e
Tx public key: 21e5aca1733e1ba68413eef97155be14a0514573f5b59184ca1111897f70b3fb
Timestamp: 1582288854 Timestamp [UCT]: 2020-02-21 12:40:54 Age [y:d:h:m:s]: 04:223:21:45:14
Block: 69446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1052598 RingCT/type: yes/0
Extra: 0121e5aca1733e1ba68413eef97155be14a0514573f5b59184ca1111897f70b3fb021100000005d81c26c0000000000000000000

1 output(s) for total of 361.332543135000 dcy

stealth address amount amount idx
00: 02303132559239850e57430d876159da606c77c3c935279d28bd073d0853b03c 361.332543135000 128098 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": 69456, "vin": [ { "gen": { "height": 69446 } } ], "vout": [ { "amount": 361332543135, "target": { "key": "02303132559239850e57430d876159da606c77c3c935279d28bd073d0853b03c" } } ], "extra": [ 1, 33, 229, 172, 161, 115, 62, 27, 166, 132, 19, 238, 249, 113, 85, 190, 20, 160, 81, 69, 115, 245, 181, 145, 132, 202, 17, 17, 137, 127, 112, 179, 251, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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