Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cc8c3fa3933432adaba1060b0d6a22141ba00c4995ce303079ff2464d519d7e

Tx prefix hash: a69242ab10b1ad5cea6943540389a90c7882360f29b6a44dff1dd95b6eeef35a
Tx public key: dd87dc71e292e5d7db3e655161103e86fc6101e79e9f1d66805fd1853f9e8d67
Timestamp: 1682285479 Timestamp [UCT]: 2023-04-23 21:31:19 Age [y:d:h:m:s]: 01:360:12:48:41
Block: 745132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518944 RingCT/type: yes/0
Extra: 01dd87dc71e292e5d7db3e655161103e86fc6101e79e9f1d66805fd1853f9e8d67021100000003e7ace25d000000000000000000

1 output(s) for total of 2.084820051000 dcy

stealth address amount amount idx
00: f153596c7e9d276e4ea1d928caca37386b25bf125c20eeb41033b7bfb8ba4abc 2.084820051000 1192553 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": 745142, "vin": [ { "gen": { "height": 745132 } } ], "vout": [ { "amount": 2084820051, "target": { "key": "f153596c7e9d276e4ea1d928caca37386b25bf125c20eeb41033b7bfb8ba4abc" } } ], "extra": [ 1, 221, 135, 220, 113, 226, 146, 229, 215, 219, 62, 101, 81, 97, 16, 62, 134, 252, 97, 1, 231, 158, 159, 29, 102, 128, 95, 209, 133, 63, 158, 141, 103, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 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