Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ce78b9bb7e75ad1feaa4a8a71ca690a5989f95e9fbe8213b5c100f6267814d2

Tx prefix hash: 343d2f84e8eb88cc5e19371cf6cc2e5f161f910767b7118c45f664d94e758c86
Tx public key: d98304a8f8f6f4aa60859f6d5f13d9991dfa64793ee2767ee341219d27c96db8
Timestamp: 1683638394 Timestamp [UCT]: 2023-05-09 13:19:54 Age [y:d:h:m:s]: 02:153:01:31:29
Block: 756359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 629158 RingCT/type: yes/0
Extra: 01d98304a8f8f6f4aa60859f6d5f13d9991dfa64793ee2767ee341219d27c96db8021100000002e7ace25d000000000000000000

1 output(s) for total of 1.913677926000 dcy

stealth address amount amount idx
00: 2f3d15f889bc1a21ee03baefd11543de3816133977bf0e734d9a26cf3ad456c2 1.913677926000 1204726 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": 756369, "vin": [ { "gen": { "height": 756359 } } ], "vout": [ { "amount": 1913677926, "target": { "key": "2f3d15f889bc1a21ee03baefd11543de3816133977bf0e734d9a26cf3ad456c2" } } ], "extra": [ 1, 217, 131, 4, 168, 248, 246, 244, 170, 96, 133, 159, 109, 95, 19, 217, 153, 29, 250, 100, 121, 62, 226, 118, 126, 227, 65, 33, 157, 39, 201, 109, 184, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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