Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55d1488fca947ea44ad76b51af480d78fb841947a69dc56e09b364e30dc74c8d

Tx prefix hash: f682cfe80bd3195e0f1c316fabe4870ccfb5df2dec62fea6c52f00f4ee500a85
Tx public key: 02d4661268a8e4ebda03de2429cd34db4fff4c295edb07e13c0d22821013e4cd
Timestamp: 1632258979 Timestamp [UCT]: 2021-09-21 21:16:19 Age [y:d:h:m:s]: 03:212:11:52:09
Block: 338367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 927806 RingCT/type: yes/0
Extra: 0102d4661268a8e4ebda03de2429cd34db4fff4c295edb07e13c0d22821013e4cd02110000001af29d7abf000000000000000000

1 output(s) for total of 46.436307272000 dcy

stealth address amount amount idx
00: 552ab254abf300cddc2b4429632667ecb92e161f106be17bb6e4137c4dc6dd68 46.436307272000 696400 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": 338377, "vin": [ { "gen": { "height": 338367 } } ], "vout": [ { "amount": 46436307272, "target": { "key": "552ab254abf300cddc2b4429632667ecb92e161f106be17bb6e4137c4dc6dd68" } } ], "extra": [ 1, 2, 212, 102, 18, 104, 168, 228, 235, 218, 3, 222, 36, 41, 205, 52, 219, 79, 255, 76, 41, 94, 219, 7, 225, 60, 13, 34, 130, 16, 19, 228, 205, 2, 17, 0, 0, 0, 26, 242, 157, 122, 191, 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