Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45179a72a3a2f01ac8d0b34f2441e074e17f4be121a81f6dbb9a5ff2520d0999

Tx prefix hash: 7d1b5b19185fbea749eab36b04f67bd311c9413b4567dfcd1f638a478ebb499c
Tx public key: 3c3e697776e3dad1e18d2172ecca3da356754503a751770ed2b40c4b94f20454
Timestamp: 1687656584 Timestamp [UCT]: 2023-06-25 01:29:44 Age [y:d:h:m:s]: 01:144:07:34:46
Block: 789670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364472 RingCT/type: yes/0
Extra: 013c3e697776e3dad1e18d2172ecca3da356754503a751770ed2b40c4b94f204540211000000014b8f5122000000000000000000

1 output(s) for total of 1.484210937000 dcy

stealth address amount amount idx
00: ce6ae0b0f780605f4c18a3f9e3271e59e10765f2bf4be86cba0f838e96c6c51f 1.484210937000 1239909 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": 789680, "vin": [ { "gen": { "height": 789670 } } ], "vout": [ { "amount": 1484210937, "target": { "key": "ce6ae0b0f780605f4c18a3f9e3271e59e10765f2bf4be86cba0f838e96c6c51f" } } ], "extra": [ 1, 60, 62, 105, 119, 118, 227, 218, 209, 225, 141, 33, 114, 236, 202, 61, 163, 86, 117, 69, 3, 167, 81, 119, 14, 210, 180, 12, 75, 148, 242, 4, 84, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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