Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f1f5ffd5807575c00bd1efbec820a8a884a7ab650c876cce9bc132b9f6b904

Tx prefix hash: f9ed6be68555d79ba447a3a47918c876dae4abc150068d6f501b1b197ad83694
Tx public key: 2bcf07e356614f49aea98964d75c6269f8fb58ae8953483857e7af744b96339e
Timestamp: 1720055281 Timestamp [UCT]: 2024-07-04 01:08:01 Age [y:d:h:m:s]: 00:274:09:42:48
Block: 1058019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196056 RingCT/type: yes/0
Extra: 012bcf07e356614f49aea98964d75c6269f8fb58ae8953483857e7af744b96339e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f2cf46d5a345ae7e911fb7ae662c33405aea4062639e2b3c7f6c51bbf1f53d6 0.600000000000 1528462 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": 1058029, "vin": [ { "gen": { "height": 1058019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f2cf46d5a345ae7e911fb7ae662c33405aea4062639e2b3c7f6c51bbf1f53d6" } } ], "extra": [ 1, 43, 207, 7, 227, 86, 97, 79, 73, 174, 169, 137, 100, 215, 92, 98, 105, 248, 251, 88, 174, 137, 83, 72, 56, 87, 231, 175, 116, 75, 150, 51, 158, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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