Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d73969aff3928adcc9b4a63c129327b31d7a1a70b3bc9f52e52f6479eb06d278

Tx prefix hash: 07f1910f070ec1992d819aaa4dd5321d17b384a91ef39ba37bcb6a3212aee33c
Tx public key: d724074e3f0798ff906344fae43836872d0957c558b2f9e1f2c3e5e2981a2609
Timestamp: 1701287344 Timestamp [UCT]: 2023-11-29 19:49:04 Age [y:d:h:m:s]: 01:087:10:37:10
Block: 902406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323623 RingCT/type: yes/0
Extra: 01d724074e3f0798ff906344fae43836872d0957c558b2f9e1f2c3e5e2981a260902110000000133af99f4000000000000000000

1 output(s) for total of 0.627992266000 dcy

stealth address amount amount idx
00: c301b291dcf4aa853d02a32d2d46ef4d5089c5ba50f55f1b70ce74618533c6b1 0.627992266000 1359045 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": 902416, "vin": [ { "gen": { "height": 902406 } } ], "vout": [ { "amount": 627992266, "target": { "key": "c301b291dcf4aa853d02a32d2d46ef4d5089c5ba50f55f1b70ce74618533c6b1" } } ], "extra": [ 1, 215, 36, 7, 78, 63, 7, 152, 255, 144, 99, 68, 250, 228, 56, 54, 135, 45, 9, 87, 197, 88, 178, 249, 225, 242, 195, 229, 226, 152, 26, 38, 9, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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