Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56e84d14fa9001598deb3d9c91c2fe038386835f670d9ad5585eb360f77d0960

Tx prefix hash: 025bda9b5ccbb5c42d3b7865901efb2a850ed5a15f34b35b0f91bdcb3de8cd9d
Tx public key: a278e508db7151520542800d7ccec8b0e440000b60396cbc7922cf7e924f4f37
Timestamp: 1590434249 Timestamp [UCT]: 2020-05-25 19:17:29 Age [y:d:h:m:s]: 04:352:17:01:16
Block: 103585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177716 RingCT/type: yes/0
Extra: 01a278e508db7151520542800d7ccec8b0e440000b60396cbc7922cf7e924f4f370211000002fd2d7572bf000000000000000000

1 output(s) for total of 278.471434653000 dcy

stealth address amount amount idx
00: 9bffaf10d08fe03bd0c6b78eae26cdace83c492bc49f0a33a051850f5d5f5eb4 278.471434653000 181522 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": 103595, "vin": [ { "gen": { "height": 103585 } } ], "vout": [ { "amount": 278471434653, "target": { "key": "9bffaf10d08fe03bd0c6b78eae26cdace83c492bc49f0a33a051850f5d5f5eb4" } } ], "extra": [ 1, 162, 120, 229, 8, 219, 113, 81, 82, 5, 66, 128, 13, 124, 206, 200, 176, 228, 64, 0, 11, 96, 57, 108, 188, 121, 34, 207, 126, 146, 79, 79, 55, 2, 17, 0, 0, 2, 253, 45, 117, 114, 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