Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eee7f284f421e59309ff93fdbb9151a4084022304fad045ce08c2dd757ef092a

Tx prefix hash: 794b7f16ff907fb705afa50b062f468caa6ff70cb548d7b2428ad589fcd4b074
Tx public key: fa751073695ae8cdc1f5ed1f24311f7109d3b719f57bbd170ece6ed7ad2a1ca8
Timestamp: 1626517619 Timestamp [UCT]: 2021-07-17 10:26:59 Age [y:d:h:m:s]: 03:136:20:12:22
Block: 295671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 869132 RingCT/type: yes/0
Extra: 01fa751073695ae8cdc1f5ed1f24311f7109d3b719f57bbd170ece6ed7ad2a1ca8021100000014c97064b9000000000000000000

1 output(s) for total of 64.316104913000 dcy

stealth address amount amount idx
00: 8ea977a9fb3c1e908b02dc159dcd33b5a1e2bd1d5d0fa9c9fcd799d85e5825a4 64.316104913000 619147 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": 295681, "vin": [ { "gen": { "height": 295671 } } ], "vout": [ { "amount": 64316104913, "target": { "key": "8ea977a9fb3c1e908b02dc159dcd33b5a1e2bd1d5d0fa9c9fcd799d85e5825a4" } } ], "extra": [ 1, 250, 117, 16, 115, 105, 90, 232, 205, 193, 245, 237, 31, 36, 49, 31, 113, 9, 211, 183, 25, 245, 123, 189, 23, 14, 206, 110, 215, 173, 42, 28, 168, 2, 17, 0, 0, 0, 20, 201, 112, 100, 185, 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