Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ca6fdd373e0d046e9828f0720cc05ec0437badf231ab49ae84433c5659f161

Tx prefix hash: 61e4997dd6d85fa85e8ff3f3995ed4fc581cf3456f6dfc7d5e981db83552e4d6
Tx public key: 258c0d47f8a74c26a95443bb468bb3718d8abdceb3572d3c0b7b7320911e5fc6
Timestamp: 1730000113 Timestamp [UCT]: 2024-10-27 03:35:13 Age [y:d:h:m:s]: 00:235:02:33:50
Block: 1140426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167726 RingCT/type: yes/0
Extra: 01258c0d47f8a74c26a95443bb468bb3718d8abdceb3572d3c0b7b7320911e5fc6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 375462eb9af8783d7bebdc5d665488a83a2e281ca506168d0986a1d69c53fbff 0.600000000000 1624223 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": 1140436, "vin": [ { "gen": { "height": 1140426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "375462eb9af8783d7bebdc5d665488a83a2e281ca506168d0986a1d69c53fbff" } } ], "extra": [ 1, 37, 140, 13, 71, 248, 167, 76, 38, 169, 84, 67, 187, 70, 139, 179, 113, 141, 138, 189, 206, 179, 87, 45, 60, 11, 123, 115, 32, 145, 30, 95, 198, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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