Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87fc43958a661c9c635a56f9eb95332bea18b7624d12edcc5484ab41d0a59a51

Tx prefix hash: fc7d1f38e8c785723cf271422a976218ad424d83438ed0432e62103af0cf62ef
Tx public key: e2347ce2e4346b2a93e4dec562d4ea5ae0f9649a26cf8fd7707e51adf1bbbd01
Timestamp: 1745809576 Timestamp [UCT]: 2025-04-28 03:06:16 Age [y:d:h:m:s]: 00:195:02:33:19
Block: 1271017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137143 RingCT/type: yes/0
Extra: 01e2347ce2e4346b2a93e4dec562d4ea5ae0f9649a26cf8fd7707e51adf1bbbd010211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3977ed3314d3dcfb1cee0a8ca1c268991b4864e3d3bc7b51febd4ed6aecc56e 0.600000000000 1758264 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": 1271027, "vin": [ { "gen": { "height": 1271017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3977ed3314d3dcfb1cee0a8ca1c268991b4864e3d3bc7b51febd4ed6aecc56e" } } ], "extra": [ 1, 226, 52, 124, 226, 228, 52, 107, 42, 147, 228, 222, 197, 98, 212, 234, 90, 224, 249, 100, 154, 38, 207, 143, 215, 112, 126, 81, 173, 241, 187, 189, 1, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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