Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca52123168f51d52be7883f0c2d78ed37c9dfe1b9cc30764dccb4f848da148f9

Tx prefix hash: ce1efd4c630300922f5efbf4947b344a41d825c849bfb25eef1381816032ec8c
Tx public key: a748e24c6c1f165f062075085e8ab083e2f2636ac50073060dd9ee7d255f1039
Timestamp: 1722903717 Timestamp [UCT]: 2024-08-06 00:21:57 Age [y:d:h:m:s]: 00:282:16:35:35
Block: 1081622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201964 RingCT/type: yes/0
Extra: 01a748e24c6c1f165f062075085e8ab083e2f2636ac50073060dd9ee7d255f1039021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 657ce3ae0b9b0cf5fd0d7500f43f4dbd4b6da1a9cbebca77dafc7dc8a6a623ad 0.600000000000 1555439 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": 1081632, "vin": [ { "gen": { "height": 1081622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "657ce3ae0b9b0cf5fd0d7500f43f4dbd4b6da1a9cbebca77dafc7dc8a6a623ad" } } ], "extra": [ 1, 167, 72, 226, 76, 108, 31, 22, 95, 6, 32, 117, 8, 94, 138, 176, 131, 226, 242, 99, 106, 197, 0, 115, 6, 13, 217, 238, 125, 37, 95, 16, 57, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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