Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7379262cd28e3aaa59088ff85267a24dcf80cd41ff9d2e18be180c45aa2f9f93

Tx prefix hash: b162fde48b2c77b52705ac98942b5919e0d94e5d644a061b14b526e2941b8169
Tx public key: 48c0d2efd2b4ce36c7957b16e2689dc2d202e52c2248aba75d1e0fca87a41a1b
Timestamp: 1751257629 Timestamp [UCT]: 2025-06-30 04:27:09 Age [y:d:h:m:s]: 00:141:08:38:17
Block: 1315601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99218 RingCT/type: yes/0
Extra: 0148c0d2efd2b4ce36c7957b16e2689dc2d202e52c2248aba75d1e0fca87a41a1b021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0ce5400590be55828b12ff95e9939a433081031ed68d0f1d34662c01a597ff 0.600000000000 1803256 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": 1315611, "vin": [ { "gen": { "height": 1315601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0ce5400590be55828b12ff95e9939a433081031ed68d0f1d34662c01a597ff" } } ], "extra": [ 1, 72, 192, 210, 239, 210, 180, 206, 54, 199, 149, 123, 22, 226, 104, 157, 194, 210, 2, 229, 44, 34, 72, 171, 167, 93, 30, 15, 202, 135, 164, 26, 27, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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