Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a228939c706f24868e711060af2c2a9a68883081ecadfea292bd7b3f7f5be03

Tx prefix hash: 4369e2fc2f693f9b12708803490d8b4c60a560614995677b7687d5382a9580df
Tx public key: 096bc29c9de6a5da77559d2b85c9c0093445bb599d810ea3d14811bc75d25ea1
Timestamp: 1730773431 Timestamp [UCT]: 2024-11-05 02:23:51 Age [y:d:h:m:s]: 00:156:10:17:00
Block: 1146779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111643 RingCT/type: yes/0
Extra: 01096bc29c9de6a5da77559d2b85c9c0093445bb599d810ea3d14811bc75d25ea1021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d37bfde0505a97f2478a0aa68f68cdedf5129e34da10f5217c8812bafffa8c25 0.600000000000 1631470 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": 1146789, "vin": [ { "gen": { "height": 1146779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d37bfde0505a97f2478a0aa68f68cdedf5129e34da10f5217c8812bafffa8c25" } } ], "extra": [ 1, 9, 107, 194, 156, 157, 230, 165, 218, 119, 85, 157, 43, 133, 201, 192, 9, 52, 69, 187, 89, 157, 129, 14, 163, 209, 72, 17, 188, 117, 210, 94, 161, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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