Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ba22a6cb1dcf589db0a4d4c5950a87b85fc91d752db4994356d11c680150125

Tx prefix hash: 87f4b11ee8bc14cc9071228659ccd1478fadb66df467a354af3cd052ecdfe1ed
Tx public key: da9af5f56ce84e0ee420b0a983e244340ea153cf38db93ea9c2b2997a0fc9fa7
Timestamp: 1735489616 Timestamp [UCT]: 2024-12-29 16:26:56 Age [y:d:h:m:s]: 00:174:06:56:49
Block: 1185836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124221 RingCT/type: yes/0
Extra: 01da9af5f56ce84e0ee420b0a983e244340ea153cf38db93ea9c2b2997a0fc9fa70211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c70d03bd7ad31c847ebd518dc7959fd9ca7e4855f1b991f0770f3b8e7119e99 0.600000000000 1672311 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": 1185846, "vin": [ { "gen": { "height": 1185836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c70d03bd7ad31c847ebd518dc7959fd9ca7e4855f1b991f0770f3b8e7119e99" } } ], "extra": [ 1, 218, 154, 245, 245, 108, 232, 78, 14, 228, 32, 176, 169, 131, 226, 68, 52, 14, 161, 83, 207, 56, 219, 147, 234, 156, 43, 41, 151, 160, 252, 159, 167, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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