Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74f171dfdfd39b5683fae2a56d388e518678b4b1319b930b81ad4db89fc70ae7

Tx prefix hash: c1940a0dcae9ce56c9ed3fe383979c4706e1ceea1fcc52495c04c9802e954fdc
Tx public key: 26983a05ae100358514fb68254386f04be5efb8cb05f1788106e05e9424d50d2
Timestamp: 1717577137 Timestamp [UCT]: 2024-06-05 08:45:37 Age [y:d:h:m:s]: 01:007:14:46:37
Block: 1037471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266309 RingCT/type: yes/0
Extra: 0126983a05ae100358514fb68254386f04be5efb8cb05f1788106e05e9424d50d202110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 444f6b8b7abc7c5f7634a1c5e30b57b7155246f74de6edb26c49dffaeaa8c379 0.600000000000 1506010 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": 1037481, "vin": [ { "gen": { "height": 1037471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "444f6b8b7abc7c5f7634a1c5e30b57b7155246f74de6edb26c49dffaeaa8c379" } } ], "extra": [ 1, 38, 152, 58, 5, 174, 16, 3, 88, 81, 79, 182, 130, 84, 56, 111, 4, 190, 94, 251, 140, 176, 95, 23, 136, 16, 110, 5, 233, 66, 77, 80, 210, 2, 17, 0, 0, 0, 14, 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