Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3db3b71c0d1f17f02f53bf8a1e64658d9ca42eed37d41d651d065042717b3fd9

Tx prefix hash: 03062768b3af128407483189513c71b4748f9f9db1d9c47ce6b2bcbffcd07a76
Tx public key: af0b5643c6944d50d813366d784968a2f87a9293b333adb98fcdef980645d10f
Timestamp: 1695937089 Timestamp [UCT]: 2023-09-28 21:38:09 Age [y:d:h:m:s]: 01:174:06:35:48
Block: 858264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385628 RingCT/type: yes/0
Extra: 01af0b5643c6944d50d813366d784968a2f87a9293b333adb98fcdef980645d10f02110000000633af99f4000000000000000000

1 output(s) for total of 0.879458053000 dcy

stealth address amount amount idx
00: bfe8076ec6db81b8f79455a6e07fe8f6329b97ecbff15f77908741f7a5c410df 0.879458053000 1312432 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": 858274, "vin": [ { "gen": { "height": 858264 } } ], "vout": [ { "amount": 879458053, "target": { "key": "bfe8076ec6db81b8f79455a6e07fe8f6329b97ecbff15f77908741f7a5c410df" } } ], "extra": [ 1, 175, 11, 86, 67, 198, 148, 77, 80, 216, 19, 54, 109, 120, 73, 104, 162, 248, 122, 146, 147, 179, 51, 173, 185, 143, 205, 239, 152, 6, 69, 209, 15, 2, 17, 0, 0, 0, 6, 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