Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca6ed7eb4503fc51825343dbeb6547d09fe5b1a8048dad70960e4a746fedc4df

Tx prefix hash: a24772e4beb669142fdf3b4cae4da7a3fbb0eb2c277dafb3c100c36d10e7a6b0
Tx public key: 241ea2277694d50addbdc8e189187fb339cb47900a62d54a20f774d0e42c37fc
Timestamp: 1720337423 Timestamp [UCT]: 2024-07-07 07:30:23 Age [y:d:h:m:s]: 00:318:02:30:10
Block: 1060357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227322 RingCT/type: yes/0
Extra: 01241ea2277694d50addbdc8e189187fb339cb47900a62d54a20f774d0e42c37fc021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 121f637ad482c3c20e31a3c183ca1187a59ba6f5fc5240674fc0a2c1d9e32e4a 0.600000000000 1530834 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": 1060367, "vin": [ { "gen": { "height": 1060357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "121f637ad482c3c20e31a3c183ca1187a59ba6f5fc5240674fc0a2c1d9e32e4a" } } ], "extra": [ 1, 36, 30, 162, 39, 118, 148, 213, 10, 221, 189, 200, 225, 137, 24, 127, 179, 57, 203, 71, 144, 10, 98, 213, 74, 32, 247, 116, 208, 228, 44, 55, 252, 2, 17, 0, 0, 0, 18, 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