Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91d612d17174089b2edcba1ce407f64cb5f50a7ab4bd77bf26a0a3458d459aa0

Tx prefix hash: b2884659791e6df86a2cd9178d9cc66ee052e220bf279d5ebd97dedf66d94172
Tx public key: df1ff02e82a71b09f042a2fc2b661853cb0e13386b7a44055e3a66cc6cb4d773
Timestamp: 1716904212 Timestamp [UCT]: 2024-05-28 13:50:12 Age [y:d:h:m:s]: 00:228:21:14:25
Block: 1031902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163794 RingCT/type: yes/0
Extra: 01df1ff02e82a71b09f042a2fc2b661853cb0e13386b7a44055e3a66cc6cb4d77302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31eebb7e659d219d0ca16be95408fa85dc4f3b696f6651939745db833d5bfb20 0.600000000000 1500351 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": 1031912, "vin": [ { "gen": { "height": 1031902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31eebb7e659d219d0ca16be95408fa85dc4f3b696f6651939745db833d5bfb20" } } ], "extra": [ 1, 223, 31, 240, 46, 130, 167, 27, 9, 240, 66, 162, 252, 43, 102, 24, 83, 203, 14, 19, 56, 107, 122, 68, 5, 94, 58, 102, 204, 108, 180, 215, 115, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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