Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bf4bc0c7d29ad501b4f92d306165b1b3815edc770d1059635d10ea22cee8733

Tx prefix hash: 8df47999989057909ec146ca5d10578bcd6c1f58acf932b86668b255a57396d7
Tx public key: 481ac5e95b4c741cad1734a53d8c1aa55e7dfa8a6575129a41541c494267a7f2
Timestamp: 1702280050 Timestamp [UCT]: 2023-12-11 07:34:10 Age [y:d:h:m:s]: 01:117:20:59:08
Block: 910645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345376 RingCT/type: yes/0
Extra: 01481ac5e95b4c741cad1734a53d8c1aa55e7dfa8a6575129a41541c494267a7f20211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8030e97ab1ab2bc7c13a8f2db09a9267324c61f85055e7f195b2d65ca93c40e6 0.600000000000 1367808 of 15

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": 910655, "vin": [ { "gen": { "height": 910645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8030e97ab1ab2bc7c13a8f2db09a9267324c61f85055e7f195b2d65ca93c40e6" } } ], "extra": [ 1, 72, 26, 197, 233, 91, 76, 116, 28, 173, 23, 52, 165, 61, 140, 26, 165, 94, 125, 250, 138, 101, 117, 18, 154, 65, 84, 28, 73, 66, 103, 167, 242, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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