Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30246a938f69640f682bd4e5f160c519c30da09adf47883d8fbc37e54fb43ab4

Tx prefix hash: b684887df29440250cd8b450dc6b18e5243505415b912a4b9fe82e08809a05d5
Tx public key: 0a1e4982b1e76e61a89e917a918f8b3a3a211f1c2aa0ad39ab74e7f100aee6dd
Timestamp: 1700944241 Timestamp [UCT]: 2023-11-25 20:30:41 Age [y:d:h:m:s]: 01:135:23:56:47
Block: 899567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358364 RingCT/type: yes/0
Extra: 010a1e4982b1e76e61a89e917a918f8b3a3a211f1c2aa0ad39ab74e7f100aee6dd02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.641742918000 dcy

stealth address amount amount idx
00: 784bbd74573c1c58c67a52f6b585c25127c79312622cb7759002fc0725868ee0 0.641742918000 1356026 of 0

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": 899577, "vin": [ { "gen": { "height": 899567 } } ], "vout": [ { "amount": 641742918, "target": { "key": "784bbd74573c1c58c67a52f6b585c25127c79312622cb7759002fc0725868ee0" } } ], "extra": [ 1, 10, 30, 73, 130, 177, 231, 110, 97, 168, 158, 145, 122, 145, 143, 139, 58, 58, 33, 31, 28, 42, 160, 173, 57, 171, 116, 231, 241, 0, 174, 230, 221, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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