Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb57a68b9807136f44fa3ef2ea4d93a3efd173f7631e3f7cf1277eb69bc62730

Tx prefix hash: a11d7e1917589de3ab89fd9a4d4dba4be0325a99db07a343bb7d7aeb76bcbc4a
Tx public key: 717f7edabc541ba1400e6b20a7e0d50ce98ff0de20ef1c85a5bd0bafc621e006
Timestamp: 1717113902 Timestamp [UCT]: 2024-05-31 00:05:02 Age [y:d:h:m:s]: 00:318:11:00:16
Block: 1033629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227612 RingCT/type: yes/0
Extra: 01717f7edabc541ba1400e6b20a7e0d50ce98ff0de20ef1c85a5bd0bafc621e00602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 507e5cc617f355e72e2c92d8bdfe317125cb979532cd6d16c347d1b81d512a38 0.600000000000 1502100 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": 1033639, "vin": [ { "gen": { "height": 1033629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507e5cc617f355e72e2c92d8bdfe317125cb979532cd6d16c347d1b81d512a38" } } ], "extra": [ 1, 113, 127, 126, 218, 188, 84, 27, 161, 64, 14, 107, 32, 167, 224, 213, 12, 233, 143, 240, 222, 32, 239, 28, 133, 165, 189, 11, 175, 198, 33, 224, 6, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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