Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18475d35b64be4bd2ff63f0d5b453da2a378cbb0f960820efedc3050edc8caad

Tx prefix hash: ffe7af31a1fa60e22ae1a53984dd98fafb0077ae46e29f2f876a8357489653e8
Tx public key: 17869ae916f39138854c98a9338d235bf4548c3a25b1df6181a5d83780f2ca50
Timestamp: 1591030150 Timestamp [UCT]: 2020-06-01 16:49:10 Age [y:d:h:m:s]: 05:153:05:29:57
Block: 104556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1297661 RingCT/type: yes/0
Extra: 0117869ae916f39138854c98a9338d235bf4548c3a25b1df6181a5d83780f2ca500211000000052d7572bf000000000000000000

1 output(s) for total of 276.416093387000 dcy

stealth address amount amount idx
00: fc2b7da60116d971dc5b6455d5446ad925f5ab42e1a77d4c5d9044b47cf5769a 276.416093387000 183165 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": 104566, "vin": [ { "gen": { "height": 104556 } } ], "vout": [ { "amount": 276416093387, "target": { "key": "fc2b7da60116d971dc5b6455d5446ad925f5ab42e1a77d4c5d9044b47cf5769a" } } ], "extra": [ 1, 23, 134, 154, 233, 22, 243, 145, 56, 133, 76, 152, 169, 51, 141, 35, 91, 244, 84, 140, 58, 37, 177, 223, 97, 129, 165, 216, 55, 128, 242, 202, 80, 2, 17, 0, 0, 0, 5, 45, 117, 114, 191, 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