Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b35dfecb18918071212c508b739f2c406b57d00b0cae1360e00a180aada07c0b

Tx prefix hash: 2c70a01084590f4ac15d3daa3cd6cfac292086cd2e2aa339ae1ca716ad177cb2
Tx public key: 8d3542658ce2a18c68fc1c1a1f029fafc8b1f50713d2dc20f571ab7bef52a56f
Timestamp: 1694778226 Timestamp [UCT]: 2023-09-15 11:43:46 Age [y:d:h:m:s]: 01:163:09:57:53
Block: 848636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377853 RingCT/type: yes/0
Extra: 018d3542658ce2a18c68fc1c1a1f029fafc8b1f50713d2dc20f571ab7bef52a56f021100000003faf35c9c000000000000000000

1 output(s) for total of 0.946491472000 dcy

stealth address amount amount idx
00: ae78a0e5920cf233b790c35ee4d4a1867bf2f17c8f0f74e9fc112a267e0c8a8f 0.946491472000 1302252 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": 848646, "vin": [ { "gen": { "height": 848636 } } ], "vout": [ { "amount": 946491472, "target": { "key": "ae78a0e5920cf233b790c35ee4d4a1867bf2f17c8f0f74e9fc112a267e0c8a8f" } } ], "extra": [ 1, 141, 53, 66, 101, 140, 226, 161, 140, 104, 252, 28, 26, 31, 2, 159, 175, 200, 177, 245, 7, 19, 210, 220, 32, 245, 113, 171, 123, 239, 82, 165, 111, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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