Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8df556872b171024f0da041912cf6cc5980812858d9e911e249f28eccd46ff8

Tx prefix hash: f74875484a083a75426fb4cd38cd04de0a2c76cb1438eddfce6cb021e93d8248
Tx public key: 34abd642d34b0a117f29eafbc97f4db7d41c16ea49d31c5ab38fb382a8180c22
Timestamp: 1730103348 Timestamp [UCT]: 2024-10-28 08:15:48 Age [y:d:h:m:s]: 00:027:11:41:32
Block: 1141251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19661 RingCT/type: yes/0
Extra: 0134abd642d34b0a117f29eafbc97f4db7d41c16ea49d31c5ab38fb382a8180c22021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a1ab39d3faa9031caa2e4297412fd3bc7f0ea35648ae748bb8efb2551ddf38f 0.600000000000 1625058 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": 1141261, "vin": [ { "gen": { "height": 1141251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a1ab39d3faa9031caa2e4297412fd3bc7f0ea35648ae748bb8efb2551ddf38f" } } ], "extra": [ 1, 52, 171, 214, 66, 211, 75, 10, 17, 127, 41, 234, 251, 201, 127, 77, 183, 212, 28, 22, 234, 73, 211, 28, 90, 179, 143, 179, 130, 168, 24, 12, 34, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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