Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c94de712ecf4eab05228a1235bfe5cdbfa34dccb073af5b86ac94666522703d

Tx prefix hash: a08608e5145cdad11b25a398301cac6aabd981458f4a64faa59bcae0010118e4
Tx public key: 1f8d7f5182b44345e2609513b16293e44c1a947424766be09ae3017a9ef6b04e
Timestamp: 1707139210 Timestamp [UCT]: 2024-02-05 13:20:10 Age [y:d:h:m:s]: 01:073:01:36:35
Block: 950918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313299 RingCT/type: yes/0
Extra: 011f8d7f5182b44345e2609513b16293e44c1a947424766be09ae3017a9ef6b04e02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0c82b66bedc989a0d1a07b5fa15be5b07207f2b4da397080562b8afc7ba98e3 0.600000000000 1409612 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": 950928, "vin": [ { "gen": { "height": 950918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0c82b66bedc989a0d1a07b5fa15be5b07207f2b4da397080562b8afc7ba98e3" } } ], "extra": [ 1, 31, 141, 127, 81, 130, 180, 67, 69, 226, 96, 149, 19, 177, 98, 147, 228, 76, 26, 148, 116, 36, 118, 107, 224, 154, 227, 1, 122, 158, 246, 176, 78, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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