Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e44c75f20a32b79c8842e9f6f863703f1ecc0de8552550adbfb055ab40185d3c

Tx prefix hash: 6552a055314e1fb065902532b78e22dfd499822e2e0aee7b3de4d1ee747e9335
Tx public key: 7eed426ae4c1c1e862c6cb1785288a8b275510cffd383a471d377dd9c9f3adbb
Timestamp: 1744868182 Timestamp [UCT]: 2025-04-17 05:36:22 Age [y:d:h:m:s]: 00:027:23:41:48
Block: 1263207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20033 RingCT/type: yes/0
Extra: 017eed426ae4c1c1e862c6cb1785288a8b275510cffd383a471d377dd9c9f3adbb0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a2dc3f73a25eb1cffc3967cb0c68f0310ebbbc6b4deb823f7e35da98ce96bac 0.600000000000 1750392 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": 1263217, "vin": [ { "gen": { "height": 1263207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a2dc3f73a25eb1cffc3967cb0c68f0310ebbbc6b4deb823f7e35da98ce96bac" } } ], "extra": [ 1, 126, 237, 66, 106, 228, 193, 193, 232, 98, 198, 203, 23, 133, 40, 138, 139, 39, 85, 16, 207, 253, 56, 58, 71, 29, 55, 125, 217, 201, 243, 173, 187, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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